Skip to main content

This is a new service – your feedback will help us to improve it.

Royal Borough of Kensington and Chelsea

Article 4 direction area

There is a problem

  • 84 issue of type invalid category value

Article 4 - No 50

reference
26
name
Article 4 - No 50
article-4-direction
26
permitted-development-rights

undefined

Minor alterations in Conservation Areas including works to windows
uprns
address-texts
geometry
MULTIPOLYGON (((-0.193820 51.496540,-0.193810 51.496540,-0.193790 51.496550,-0.193770 51.496550,-0.193740 51.496560,-0.193720 51.496570,-0.193660 51.496590,-0.193690 51.496640,-0.193660 51.496650,-0.193500 51.496690,-0.193520 51.496730,-0.193580 51.496810,-0.193600 51.496860,-0.193630 51.496900,-0.193650 51.496940,-0.193680 51.496980,-0.193710 51.497030,-0.193730 51.497070,-0.193760 51.497110,-0.193780 51.497140,-0.193790 51.497160,-0.193870 51.497140,-0.193920 51.497130,-0.193950 51.497120,-0.193970 51.497120,-0.194030 51.497100,-0.194050 51.497100,-0.194100 51.497090,-0.194150 51.497070,-0.194120 51.497020,-0.194100 51.496980,-0.194070 51.496940,-0.194050 51.496900,-0.194020 51.496850,-0.193990 51.496810,-0.193970 51.496770,-0.193940 51.496730,-0.193920 51.496690,-0.193890 51.496640,-0.193860 51.496600,-0.193830 51.496550,-0.193830 51.496540,-0.193820 51.496540)))
point
POINT (-0.193823 51.496865)
notes
entry-date
2025-01-03
start-date
end-date

How to fix this issue

Your data is missing a permitted-development-rights.

The Article 4 direction area guidance explains how to fix the issue:

permitted-development-rights

A list of the permitted development rights withdrawn by the article 4 direction.

Separate the rights in the list using semicolons.

Only use rights from our permitted development right dataset. If the area withdraws a permitted development right that is not in our dataset, email digitalland@communities.gov.uk.

Example: 3D;3M;11B

How to improve Royal Borough of Kensington and Chelsea’s data

  1. Fix the errors indicated
  2. Use the check service to make sure the data meets the standard
  3. Publish the updated data on the endpoint URL